Database Operations
As the previous sections discussed, you can upgrade your V12 database to the latest version as part of the ActiveBatch 2024.x or later installation process. If you are testing the latest version, you may need to update a V12 database to the latest version more than once as part of your overall testing strategy. That is, while keeping your V12 environment going while testing 2024.x, additional objects may have been created in V12 (after the initial 2024.x installation), and those objects (typically jobs/plans) need to be tested in 2024.x. This is where ActiveBatchDB.msi will come in handy.
ActiveBatchDB.msi is must to be run on an ActiveBatch 2024.x system. You will need to have performed an ActiveBatch 2024.x installation (including the Job Scheduler component) before you can run the ActiveBatchDB.msi.
ActiveBatchDB.msi does not install any ActiveBatch software. Its sole purpose is to either create a new empty 2024.x database (or Tablespace) OR to promote an existing V12 database to the current version database.
Note: You must run the ActiveBatchDB.msi procedure on an existing 2024.x installed Job Scheduler system. No software is installed. It is designed to promote a V12 database to a 2024.x database.
Start the ActiveBatchDB.msi installation kit. You will be presented with a welcome window. Click Next to continue. Read, then accept the license agreement. Click Next. Enter Customer information (User Name and Organization, if desired). Click Next.
You will be presented with a list of possible database types to select, as depicted in the image below. Choose the database type that you are using for the ActiveBatch backend database. In this example, MS SQL Server Family is selected. Click Next.
After selecting the database, you will be prompted to create an empty database or initialize an existing one.
Note: For the ActiveBatchDB procedure, the default is to “Initialize or update an existing database”. This is due to the expectation that most uses of this procedure will be to promote a V12 database several times for testing purposes before moving to production.
The above dialog requests that you either: (1) Create a new empty 2024.x database (2) Initialize or update an existing database. Since this section is discussing updating an existing database from V12 to 2024.x, keep this default selection, then click Next.
The above dialog requires you specify the server name where the V12 ActiveBatch database resides. In continuing with the SQL Server example, a SQL Server name is entered. From there, specify the type of credentials used to access the database – a SQL Server database account or a Windows account. If you are using a SQL Server database account for database access, enter the username and password. If you are using a Windows account, leave these fields blank (these fields are NOT for Windows credentials, they are only used when using a SQL database account for access).
Note: For the Server Name field, you can also specify a specific SQL Server instance name with the syntax “hostname\instance-name”. Click Next to continue.
Select the ActiveBatch V12 database from the list of SQL Server databases. In this example, AbatDB is selected. Click Next to continue.
The above dialog appears when the system detects you are running the database kit on a 2024.x ActiveBatch Scheduler and selected a V12 database to update. It will update the V12 database to 2024.x. Typically, you would want the objects disabled when the purpose of the database update is to continue testing 2024.x. You likely do not want the Scheduler to start running jobs after the database update. The other option is to leave the objects in their current state. If that is selected, key objects will not be disabled, and when the upgraded database is referenced in the test 2024.x Scheduler’s connection string, the Scheduler will begin dispatching and running jobs as usual, without requiring the enabling of objects.
When ready, Click Install. The database will be updated. As a reminder, no software is installed.